Release 0.14.3#2980
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release readiness review (v0.14.2 -> TARGET a7531f0)
This is a release readiness report done by
$final-release-reviewskill.Diff
v0.14.2...a7531f0
Release call:
🟢 GREEN LIGHT TO SHIP patch release with fixes and expanded cross-platform coverage; no concrete release-blocking regressions identified.
Scope summary:
Risk assessment (ordered by impact):
src/agents/sandbox/workspace_paths.py,src/agents/sandbox/session/base_sandbox_session.py, andsrc/agents/sandbox/sandboxes/__init__.py; new tests intests/sandbox/test_workspace_paths.pyandtests/sandbox/test_sandboxes_import.py; Windows job added in.github/workflows/tests.yml.uv run pytest tests/sandbox/test_workspace_paths.py tests/sandbox/test_sandboxes_import.pyand ensure all pass on Linux/Windows CI.close()now invalidates future connection use and closes all tracked worker-thread connections, which is correct lifecycle behavior but worth validating for threaded consumers._closedguard and connection tracking added insrc/agents/memory/sqlite_session.py; regression coverage added intests/test_session.py(test_sqlite_session_close_closes_worker_thread_connections).uv run pytest tests/test_session.py -k sqlite_session_close_closes_worker_thread_connectionsand confirm connection-use-after-close raises expectedsqlite3.ProgrammingError.Notes:
git tag -l 'v*' --sort=-v:refname | head -n1(v0.14.2).a7531f0c08de83a5ed1cc94cc1e1e6f4d3cc83cc).$code-change-verificationcoverage for target commit.